Lynx:

• BetaProgramInitiator (Verified): https://mumbai.polygonscan.com/address/0xb6e6512F4c9A74Ef1b742d832852769F3CEE646c#code
• Granted initiator role:
  https://mumbai.polygonscan.com/tx/0x67cf6b0b4dfaa1e2634cf97259e9256bb9261a8fca84b5b9640d305e81c882fa

NOTE: We may need to update the Coordinator implementation contract on Lynx - it didn't have the feeDeduction method needed by the BetaProgramInitiator contract.

Tapir:

• BetaProgramInitiator (Verified):
  https://mumbai.polygonscan.com/address/0x070fbc5a82776A1fd9945824d0719E4E7a5Ac01c#code
• Granted initiator role: https://mumbai.polygonscan.com/tx/0x352450f0f3c4bf0f08757b0eb94b3420103f2a76941e8b52861d6e097dcc2c6f

Fresh Coordinator implementation contract deployed at https://mumbai.polygonscan.com/address/0x90e112651a57f1484279b9da5c0bd3380e59ceea#code for lynx, and lynx Coordinator proxy contract updated to point to new contract.

Fresh Coordinator implementation contract deployed at

We need to include these changes in this PR, right?

And that would mandate a bump in @nucypher/nucypher-contracts, na hence @nucypher/taco? We don't need to coordinate it with nucypher/nucypher, right?

We need to include these changes in this PR, right?

Yes. One minor update to the ABI in the registry for the feeDeduction method in Coordinator - included now.

We don't need to coordinate it with nucypher/nucypher, right?

From the nucypher/nucypher side it's not needed immediately for functionality because the feeDeduction method (the reason for the update) is not used by the nodes/python code. It is used by the BetaProgramInitiator contract which we can now directly test on lynx and tapir.

And that would mandate a bump in @nucypher/nucypher-contracts, na hence @nucypher/taco?

I suspect taco-web doesn't use feeDeduction either. so no update needed there - but you can let me know if it does.

An update will occur eventually as part of 7.1.x, but I don't think it needs to be immediate because neither client nor server-side need it at the moment.

I suspect taco-web doesn't use feeDeduction either - but you can let me know if it does.

It doesn't, but I still need to use the new Coordinator contract for everything else.

Ok, I think I can implement it now without breaking anything / waiting for 7.1.x.

It doesn't, but I still need to use the new Coordinator contract for everything else.

Coordinator is proxied so you are still interacting with the same proxy contract, it's the underlying implementation contract that changed, and that change was an added method which is not used by the client/server libraries.